Solution: WhoisFreaks
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊
| Attribute | Value |
|---|---|
| Publisher | WhoisFreaks |
| Support Tier | Partner |
| Support Link | https://whoisfreaks.com |
| Categories | Security - Threat Intelligence,Security - Threat Protection |
| Version | 3.0.2 |
| Author | WhoisFreaks - support@whoisfreaks.com |
| First Published | 2026-09-30 |
| Last Updated | 2026-10-21 |
| Solution Folder | WhoisFreaks |
| Marketplace | Azure Marketplace · Popularity: 🔵 Medium (74%) |
The WhoisFreaks solution for Microsoft Sentinel ingests commercial threat intelligence and newly registered domain (NRD) feeds through the Codeless Connector Framework into custom Log Analytics tables for hunting, detection, and investigation.
Underlying Microsoft Technologies used:
This solution depends on technologies that may be in Preview or incur additional ingestion or operational costs:
a. Azure Monitor data collection rules
A WhoisFreaks API subscription and key entitled to the selected feeds are required.
This solution provides 1 data connector(s):
This solution uses 3 table(s):
| Table | Used By Connectors | Used By Content |
|---|---|---|
WhoisFreaksNRDNoWhois_CL |
WhoisFreaks Threat & NRD Feeds (via Codeless Connector Framework) | Analytics |
WhoisFreaksNRD_CL |
WhoisFreaks Threat & NRD Feeds (via Codeless Connector Framework) | Analytics |
WhoisFreaksThreat_CL |
WhoisFreaks Threat & NRD Feeds (via Codeless Connector Framework) | Analytics |
This solution includes 4 content item(s):
| Content Type | Count |
|---|---|
| Analytic Rules | 4 |
| Name | Severity | Tactics | Tables Used |
|---|---|---|---|
| WhoisFreaks - burst of newly registered domains | Low | ResourceDevelopment | WhoisFreaksNRDNoWhois_CLWhoisFreaksNRD_CL |
| WhoisFreaks - high confidence threat domains | High | InitialAccess, CommandAndControl | WhoisFreaksThreat_CL |
| WhoisFreaks - newly registered domain seen in threat feed | High | InitialAccess, ResourceDevelopment | WhoisFreaksNRDNoWhois_CLWhoisFreaksNRD_CLWhoisFreaksThreat_CL |
| WhoisFreaks - parked threat domains | Medium | ResourceDevelopment | WhoisFreaksThreat_CL |
📄 Source: WhoisFreaks/README.md
This solution ingests WhoisFreaks threat intelligence and newly registered domain (NRD) feeds using the Microsoft Sentinel Codeless Connector Framework (CCF). Threat API fields are retained in WhoisFreaksThreat_CL (including threat_type); WHOIS NRD API fields are retained in WhoisFreaksNRD_CL; headerless no-WHOIS rows are written to WhoisFreaksNRDNoWhois_CL with the payload column domain_name. Both NRD tables include an nrd_type column (gtld or cctld) set by the DCR transform so gTLD and ccTLD rows can be distinguished without parsing the domain. TimeGenerated is the Log Analytics system ingestion timestamp. The connector UI lets users select feeds enabled by their subscription. The selection is a form and is not read back after the page reloads; the connector page's Data received chart shows one line per feed, so a feed with no line is not enabled. To change the enabled feeds, disconnect, reselect, and connect again. The two NRD tables are created with 30-day retention because the NRD analytic rules look back 7 and 8 days; the threat table is created with 4-day retention because its rules read at most the last six hours and the full threat feed is re-ingested daily. Workspaces that installed an earlier version keep their original table retention; raise the NRD tables with az monitor log-analytics workspace table update --retention-time 30 --total-retention-time 30 for WhoisFreaksNRD_CL and WhoisFreaksNRDNoWhois_CL. The solution also includes four scheduled analytic rules.
az login).Do not commit API keys, generated parameter files containing secrets, or deployment outputs with secrets. Supply the key through a protected shell variable or a secret manager.
The source connector configuration is in Data Connectors/WhoisFreaks_CCF/. Validate and package the solution with the repository's V3 build-and-validation flow. The solution manifest lists the four analytic-rule YAML files so the generated package includes their templates.
The connector UI offers a multi-select feed list. Select only feeds included in the API subscription. Test in staging first; successful deployment and data ingestion depend on the target workspace and feed entitlements.
The four rule source files are in Analytic Rules/. Before packaging or deploying a rule:
query value from the rule YAML and run it as KQL. The query must compile; zero matches is valid when the data does not meet the detection condition.[Content truncated...]
| Version | Date Modified (DD-MM-YYYY) | Change History |
|---|---|---|
| 3.0.2 | 21-10-2026 | Fixed Data Connector feed selection, API key handling, duplicate fetches and table retention. Fixed Analytic Rules confidence threshold, NRD burst baseline, parked-domain flag and hourly re-alerting. |
| 3.0.1 | 16-10-2026 | Deployment UI now filters workspaces by the exact resource group and lets the workspace region be reviewed before deployment. |
| 3.0.0 | 09-10-2026 | Initial publication with the CCF threat and NRD feeds and four analytic-rule templates. |
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊